home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 26
/
Cream of the Crop 26.iso
/
os2
/
iserv300.zip
/
ISERVER.DOC
< prev
next >
Wrap
Text File
|
1997-07-26
|
15KB
|
358 lines
▀ █▀▀ █▀▀ █▀█ █ █ █▀▀ █▀█
█ ▀▀█ █▀ █▀▄ █ █ █▀ █▀▄ I n t e r n e t S e r v e r R e l a y
▀ ▀▀▀ ▀▀▀ ▀ ▀ ▀ ▀▀▀ ▀ ▀
Copyright Multiboard Communications, 1994-1997
All rights reserved.
What does this program do?
══════════════════════════════════════════════════════════════════════─────
iServer will import email from a fidonet netmail format directly into
your RemoteAccess system as internet email. No longer will your users
have to know anything about addressing to "UUCP" at some obscure netmail
address. Of course, it will also export outbound mail from your BBS and
prepare them in a netmail fashion, ready to be gated out.
A complete solution!
══════════════════════════════════════════════════════════════════════─────
iServer is not only a tosser for your mail, but a powerful server engine
as well. iServer can automatically bounce mail addressed to unknown
users on your system, or repond to inbound messages automatically. With
iServer and its request/respond system, you can build powerful applica-
tions to interface with your basic email system, such as info-bots,
listserv and ftpmail. Outbound messages can be restricted on site, user
security settings and the number of messages posted per user. You also
have the option to restrict file transfers via email, such as UUENCODED,
BASE64 or MIME formatted messages.
iServer integrates completely and seemlessly with your RemoteAccess
system, using it's data files for user verification, as well as obtaining
user security information for its message restricting features.
■ Seamless integration with RemoteAccess 2.x
■ Direct import/export of email
■ Powerful server response engine
■ Bounce messages to unknown users
■ Merge mailing lists as usegroups
■ Restrict certain sites, functions or encoded files
■ Custom templates for bounce messages
■ Dumb address checking
■ Disclaimer message support
What do I need to set this program up?
══════════════════════════════════════════════════════════════════════─────
In order to use this program you will need:
1) Your system to use a fidonet style frontend mailer that *.MSG files
in it's inbound/outbound netmail directory. (for example: FrontDoor,
Intermail and a number of others)
2) RemoteAccess 2.x or another BBS software package that can use the
JAM message base format.
Basic setup method:
1) Create a message base on your BBS. For RemoteAccess, it should
be an "Internet" or "Echomail" style area, "JAM" type with the
"Private" mail only setting. This is not the same as your
regular netmail area.
2) Run ISERVCFG.EXE to setup iServer. (there is lots and lots of
online help, just press F1)
3) Put ISERVER.EXE in your RUNBBS.BAT file, after receiving netmail
and after the user logs off (or optionally during an event)
4) You're done!
Advanced setup method:
This method, albeit a little more involved, will provide you with
the best setup, since it keeps your netmail and internet email
completely seperate from each other.
Lets assume for this example that your standard fidonet address
is 7:8/9, you would:
1) Complete steps 1 & 2 from the basic setup
2) Create an aka in your mailer of 7:8/9.999
3) Setup your site address in ISERVCFG as the above
(* THIS IS THE BIG PART *)
4) Setup your netmail tosser to ignore mail to 7:8/9.999.
(not import it into the netmail area in your BBS, since iServer
is the one that should be doing the importing for this mail)
Doing this means that your netmail/echomail tosser will never
accidentally grab the inbound mail that is meant for iServer.
If you do not use this advanced method, it means you must
*always* run iServer before your tosser imports netmail.
5) You're done! It really isn't much more difficult, but with
this method you can be sure that you will never have your
email and netmail crossed anywhere.
What can't I do until I register?
══════════════════════════════════════════════════════════════════════─────
Nothing. The only limits that are imposed, are that you can only
have a maxium of 3 RESPOND entries, and 3 RESTRICTS until registered.
You also cannot use any TABLE entries until you have registered.
It will also remove the unregistered notice, and the 2 second delay.
Please register, a lot of effort went into developing the program,
and the price is quite reasonable.
Please note that registration keys are built on your site address
and site name, so make sure that they are correct.
Special files
══════════════════════════════════════════════════════════════════════─────
ADDRESS.BAD - Custom message to send when the user has addressed
a message to what appears to be an invalid account.
LIMIT.BAD - Custom message to send when a user does not have
sufficient credit to post a message.
SITE.BAD - Custom message to send when a user posts to a site
that you have marked as restricted.
SUBJECT.BAD - Custom message to send when a user attempts to post
to a function that you have restricted.
USER.BAD - Custom message to send to the originator of a message
when an inbound message is not addressed to anyone
valid on your system.
UUENCODE.BAD - Custom message to send when a user attempts to pass
a encoded file through your gateway.
DISCLAIM.MSG - A custom disclaimer to add to the bottom of your
outgoing messages. Delete this file if you do not
want one.
RESPOND.MSG - A custom template for creating request/respond
files during a 'RESPOND' command. If you wish to
use the standard one (compatible with version 1.x)
simply delete this file.
Metalist Commands
══════════════════════════════════════════════════════════════════════─────
This is a list of the valid metastrings that can be used in return
messages, request 'return' files and 'respond' returned text files.
%TO% - Who the message is to
%FROM% - Who the message if from
%DATE% - The date of the message
%SUBJECT% - The subject of the message
%WHERETO% - The Fidonet destination
%WHEREFROM% - The Fidonet source
%SITENAME% - The name of the processing site
%SERVER% - The name of the processing server
%SITEADDR% - The Fidonet address of the site
%UUCPADDR% - The Fidonet address of the gate
%ORIGTO% - Who the message was originally to *
%ORIGFROM% - Who the message was originally from *
%ORIGSUBJECT% - The original subject of the message *
.TO. - Who the message is to .
.FROM. - Who the message if from .
.ORIGTO. - Who the message was originally to .
.ORIGFROM. - Who the message was originally from .
^TO^ - Who the message is to ^
^FROM^ - Who the message if from ^
^ORIGTO^ - Who the message was originally to ^
^ORIGFROM^ - Who the message was originally from ^
Notes:
* Normally the "ORIG" values are the same as the normal to/from/subject
except when messages are being returned or re-routed.
. Same as normal, except replacing doing a period->underscore and a
space->period conversion of the standard text.
^ Same as normal, except autocapitized versions of the standard text.
For example: "pete rocca" becomes "Pete Rocca"
Command line parameters
══════════════════════════════════════════════════════════════════════─────
Typing ISERVER /? will bring up a list of command line options.
Normally, just running ISERVER.EXE is sufficient, but there are
other options available.
Import/export mail parameters
/PROCESS Standard behaviour (default)
/FORCE Ignore last scanning markers
/NOMARK Do not update high scan marks
/NOSCAN Do not scan for outgoing mail
/NOTOSS Do not toss incoming mail
Online programs and parameters
/USERID droppath Userid creation (if flag not toggled)
/USERID droppath /FORCE Userid creation (always)
Utilities
/TABLE tablename [+|-]user Add/remove user from a table
What is /USERID?
This program simply gives the user an interface to change their
user alias to something that looks more professional on the internet
if they wish. You can setup restrictions for this alias in the
ISERVCFG program.
To implement this, you would change the message area on the BBS to
"Use Handles Only" which would then post the message from their
alias. This way, they can have a name like "roccap@yoursite.com"
if they choose.
The online program options are to run the userid (handle creation)
part of the program. The /FORCE overrides if the user has already
set the user flag as defined in ISERVCFG.
Examples: ISERVER.EXE /USERID c:\ra\node1 /FORCE
ISERVER.EXE /USERID c:\ra
ISERVER.EXE /USERID c:\ra\node2
Please note that this utility is completely optional and not required
for the operation of iServer.
What is /TABLE?
Tables are simular to "Responds", except you can put a class of
user names into a table rather than having a seperate trigger
for each user.
For example, you could have a table of users that were on
vacation, and if someone posted a message to a user that was in
the vacation table, it could send them back a message saying
that they would be delayed in responding. You could also have
a table of bad users, and have their inbound mail deleted.
To insert a user into a table, use the following command:
ISERVER /TABLE tablename +User Name
To remove a user from a table, replace the plus sign (+) with a minus
sign (-). In the vacation table example, you could allow an option
from your BBS that allowed them to toggle their own status.
For example:
Vacation
(Y)es .. would run ISERVER /TABLE VACATION +*F *L
(N)o .. would run ISERVER /TABLE VACATION -*F *L
Where your BBS would replace *F *L with the user name.
Please note that this utility is completely optional and not required
for the operation of iServer.
Online help
══════════════════════════════════════════════════════════════════════─────
The ISERVCFG.EXE program has complete context-sensitive help online
to provide the easiest method of setting up. Simply press F1 from
almost anywhere in the program for help about the menu you are in.
Function logging legend
══════════════════════════════════════════════════════════════════════─────
■ - Program startup
I - Import message
E - Export message
B - Bounce message (Unknown user on this system)
T - Infobot trigger response
M - Merge mailing list
X - Table trigger response
R - Restricted
C - Consume message (Circular route detection)
U - Userid selected
License and disclaimer
══════════════════════════════════════════════════════════════════════─────
"iServer" (also known as "ISR") is NOT free.
It is being marketed under the "try before you buy" or shareware
concept. You are entitled to use ISR for a period up to forty-five
(45) days, after which you MUST register or stop using the program.
Registration entitles you to use ISR as well as any future versions
of this program that may or may not be released, subject to any
additional licensing conditions which may be attached.
Registration will also allow you to you the full ability of iServer
as well as remove the unregistered notice. It will also help to
continue to develop this program. (not to mention maintain the
legality of this agreement)
By running any of the executable programs included, you agree that
Pete Rocca, Multiboard Communications nor any affiliates of the
above mentioned are responsible for any damage ever experienced,
however so created. If you cannot agree to this, then your privilege
to use any of these programs is revoked and it becomes illegal for
you to execute any programs included with this documentation.
You may freely copy and distribute the shareware version of ISR as
long as its original archived contents are not modified in any way.
You may NOT distribute any registration keys without the express
written consent of Pete Rocca of Multiboard Communications.
You may not use a registration number that is not licensed from
Multiboard Communications directly to you.
It is illegal to edit, alter, hack, reverse engineer and / or modify
any components of the ISR archive in any manner.
If dispute of any issues on legal grounds said above, then governing
law of Ontario, Canada will rule.
Support
══════════════════════════════════════════════════════════════════════─────
iServer is now freeware and does not have any author support. You
can visit our web site which has product information and tips and
tricks. We also have a Fidonet echo MCC_SUPPORT which is a great
peer support echo.
http://www.multiboard.com/
ftp://ftp.multiboard.com/
Acknowledgments
══════════════════════════════════════════════════════════════════════─────
Requires at least DOS 3.3 and SHARE.EXE loaded for the JAM routines.
Thanks to the public domain swapping utils that required very little
in the way of tweaking, by Thomas Wagner. iServer/ISR are copyrighted
products by Multiboard Communications and Pete Rocca.